--- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@...> wrote:
>
> Hi Ray,
>  
> You are correct but that is considered a feature :}
>  
> You can even re-boot the PC and KFLOP will maintain its state.  This way the destinations, encoder positions, IO, Internal variables are all maintained which is what I think you would most often want.
>  
> The only solution we currently offer is to force a known state if you wish to do so.  I think it might be good practice to set everything in the board that you are using and not rely on default values anyway.
>  
> Regards
> TK
>  
>  
>
> From: himykabibble <jagboy@...>
> To: DynoMotion@yahoogroups.com
> Sent: Saturday, January 7, 2012 5:27 PM
> Subject: [DynoMotion] KMotion_dotNet Startup Initialization
>
>
>  
> I have much of my CNC app working, but I'm having some startup problems. It appears to me that the board is retaining state between sessions, if I don't power it down. I can see this most easily by loading a G-code file, starting it running, then hitting FeedHold. If I then exit my app, and re-start it, it comes up in FeedHold. I can see no way to force a complete re-initialization of the board. Obviously I could force all the necessary states on start-up, but it seems to me the board NEEDS to be put into a known state when an app starts, or, at a minimum the app needs to have a way of forcing the board into a known state more efficiently than by setting them all individually in the app.
>
> What am I missing?
>
> Regards,
> Ray L.
>

--- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@...> wrote:
>
> Hi Ray,
>  
> You are correct but that is considered a feature :}
>  
> You can even re-boot the PC and KFLOP will maintain its state.  This way the destinations, encoder positions, IO, Internal variables are all maintained which is what I think you would most often want.
>  
> The only solution we currently offer is to force a known state if you wish to do so.  I think it might be good practice to set everything in the board that you are using and not rely on default values anyway.
>  
> Regards
> TK
>  
>  
>
> From: himykabibble <jagboy@...>
> To: DynoMotion@yahoogroups.com
> Sent: Saturday, January 7, 2012 5:27 PM
> Subject: [DynoMotion] KMotion_dotNet Startup Initialization
>
>
>  
> I have much of my CNC app working, but I'm having some startup problems. It appears to me that the board is retaining state between sessions, if I don't power it down. I can see this most easily by loading a G-code file, starting it running, then hitting FeedHold. If I then exit my app, and re-start it, it comes up in FeedHold. I can see no way to force a complete re-initialization of the board. Obviously I could force all the necessary states on start-up, but it seems to me the board NEEDS to be put into a known state when an app starts, or, at a minimum the app needs to have a way of forcing the board into a known state more efficiently than by setting them all individually in the app.
>
> What am I missing?
>
> Regards,
> Ray L.
>

--- In DynoMotion@yahoogroups.com, "bradodarb" <bradodarb@...> wrote:
>
>
> Ray, I think Tom is right on this one. Your intial state requirements may be different than mine, so the calling application needs to be responsible for the initialzation.
>
> -Brad Murry
> --- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@> wrote:
> >
> > Hi Ray,
> >  
> > You are correct but that is considered a feature :}
> >  
> > You can even re-boot the PC and KFLOP will maintain its state.  This way the destinations, encoder positions, IO, Internal variables are all maintained which is what I think you would most often want.
> >  
> > The only solution we currently offer is to force a known state if you wish to do so.  I think it might be good practice to set everything in the board that you are using and not rely on default values anyway.
> >  
> > Regards
> > TK
> >  
> >  
> >
> > From: himykabibble <jagboy@>
> > To: DynoMotion@yahoogroups.com
> > Sent: Saturday, January 7, 2012 5:27 PM
> > Subject: [DynoMotion] KMotion_dotNet Startup Initialization
> >
> >
> >  
> > I have much of my CNC app working, but I'm having some startup problems. It appears to me that the board is retaining state between sessions, if I don't power it down. I can see this most easily by loading a G-code file, starting it running, then hitting FeedHold. If I then exit my app, and re-start it, it comes up in FeedHold. I can see no way to force a complete re-initialization of the board. Obviously I could force all the necessary states on start-up, but it seems to me the board NEEDS to be put into a known state when an app starts, or, at a minimum the app needs to have a way of forcing the board into a known state more efficiently than by setting them all individually in the app.
> >
> > What am I missing?
> >
> > Regards,
> > Ray L.
> >
>

--- In DynoMotion@yahoogroups.com, "himykabibble" <jagboy@...> wrote:
>
> Brad,
>
> I can see the logic, but in 30 years of doing embedded system development, I can't think of a single system I've ever worked on that didn't have some programmatic means of forcing the hardware into a known consistent state, as a starting point for any unique configuration the application may want to do. It can obviously be worked around, but I need to know EXACTLY what NEEDS to be re-initialized to ensure there won't be corner cases where I end up in an unexpected state. And what do I do if the DSP crashes - I'm sure it's possible for that to happen, however rare. As I said, my board is normally locked inside sealed enclosure, so cycling power is really not convenient.
>
> Regards,
> Ray L.
>
> --- In DynoMotion@yahoogroups.com, "bradodarb" <bradodarb@> wrote:
> >
> >
> > Ray, I think Tom is right on this one. Your intial state requirements may be different than mine, so the calling application needs to be responsible for the initialzation.
> >
> > -Brad Murry
> > --- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@> wrote:
> > >
> > > Hi Ray,
> > >  
> > > You are correct but that is considered a feature :}
> > >  
> > > You can even re-boot the PC and KFLOP will maintain its state.  This way the destinations, encoder positions, IO, Internal variables are all maintained which is what I think you would most often want.
> > >  
> > > The only solution we currently offer is to force a known state if you wish to do so.  I think it might be good practice to set everything in the board that you are using and not rely on default values anyway.
> > >  
> > > Regards
> > > TK
> > >  
> > >  
> > >
> > > From: himykabibble <jagboy@>
> > > To: DynoMotion@yahoogroups.com
> > > Sent: Saturday, January 7, 2012 5:27 PM
> > > Subject: [DynoMotion] KMotion_dotNet Startup Initialization
> > >
> > >
> > >  
> > > I have much of my CNC app working, but I'm having some startup problems. It appears to me that the board is retaining state between sessions, if I don't power it down. I can see this most easily by loading a G-code file, starting it running, then hitting FeedHold. If I then exit my app, and re-start it, it comes up in FeedHold. I can see no way to force a complete re-initialization of the board. Obviously I could force all the necessary states on start-up, but it seems to me the board NEEDS to be put into a known state when an app starts, or, at a minimum the app needs to have a way of forcing the board into a known state more efficiently than by setting them all individually in the app.
> > >
> > > What am I missing?
> > >
> > > Regards,
> > > Ray L.
> > >
> >
>